Skip to content

Clarify build context file inclusion#1159

Closed
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-build-context-file-inclusion
Closed

Clarify build context file inclusion#1159
radiantjade wants to merge 1 commit into
railwayapp:mainfrom
radiantjade:clarify-build-context-file-inclusion

Conversation

@radiantjade
Copy link
Copy Markdown
Contributor

Summary

  • clarify how GitHub deployments choose files from the selected repository and Root Directory
  • distinguish CLI archive behavior from GitHub source snapshots for .gitignore handling
  • point users to .dockerignore when they need to exclude files from Railpack or Dockerfile build context

Related Central Station question: https://station.railway.com/questions/railpack-silently-excludes-large-committ-dd87954e

Verification

  • build started ...
    ... finished build of 2 collections and 299 documents in 4461ms

Users were conflating GitHub source snapshots, CLI archives, and .gitignore behavior when debugging missing files in build outputs. This adds a small source-context note to the build configuration docs and aligns the CLI deployment page with the same distinction.

Constraint: Keep the change doc-only and directly tied to build-context troubleshooting.

Rejected: Add platform size-limit claims | no public evidence for a per-directory Railpack cap.

Confidence: medium

Scope-risk: narrow

Tested: git diff --check; pnpm exec content-collections build
@brody192 brody192 closed this May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants